Intelligent client cache mashup for the traveler

ABSTRACT

A data mashup on a user&#39;s device. The preferred and probably most useful device is a mobile one. However, there is no reason to so limit the invention. When the user makes an application data entry, such as a calendar entry for a meeting with a customer, the mashup uses rules and data patterns that have been defined by the user to query other relevant information sources to collect related information about the customer or the meeting, and to cache the collected information on the device for the user.

TECHNICAL FIELD

The invention relates to automated services, and especially to theautomated collection of data and information for personal informationmanagers, personal data assistants (PIM and PDAs), laptops and any typeof electronic device that individuals might use in a mobile environmentfor the containment of personal and business information.

BACKGROUND OF THE INVENTION

Many of today's organizations are going global, meaning that employeeslocated in one geography might need to interact with their counterpartsand customers in another remote geography. In a recent survey conductedin the US, it was found that, last year, American “road warrior”s(business people) took 207 million business trips, spending an averageof about three and a half days away from the office per trip.(http://www.media3pub.com/usbank/articles/road_warrior.html ). Becauseof this shifting paradigm, employees are often working at remotelocations with limited or no real-time access to needed corporate orpersonal information.

One of the big inhibitors to productivity in this environment is theinability to access needed information to accomplish short term tasks,like finding the right person in a back-office to answer a question, orperhaps reviewing the purchase history of a customer before tomorrow'smeeting . Even though many organizations have their own corporatedirectory holding employee and customer information, they need a way toalways have access at their mobile devices to the latest and authenticinformation available, along with important related businessinformation.

What is needed is a way to ensure that important information isavailable in one's laptop or mobile device, regardless of where the usermight be.

The above problem statement brings forth bevi of issues, including thesize of corporate databases that encompass multimedia elements, such asgraphics, pictures, maps, even video presentations. Important businessinformation might also include information found in customer relationsmanagement (CRM) systems, social link networks, blogs, etc.

According to the Wikipedia “website (http://www.wikipedia.org/), amashup is a website or web application that uses content from more thanone source to create a completely new service. The origin of the term“mashup” comes from the music industry where a DJ mixes a vocal trackfrom one song with the instrumental track of another. Recently, mashupshave started to appear in non-browser based applications like instantmessaging, where plug-ins are used to produce compositions ofinformation for end users, like showing directory and social networkingdata in a chat window. The focus of mashups at the present has been onproducing real time compositions for an end user.

There is a long history of caching techniques for specific applicationdomains, such as for relational databases, email systems, and for edgeservers in the web. Some of these cache techniques have intelligentfeatures that preload elements of the associated application domains.For example, one known email application fetches copies of emailmessages when their titles appear on screen in representation of thein-box?; a known database application prefetches related table subsetswhen some table rows are retrieved, if there has been a history of thedatabase application using a query to “join” these related tablesubsets.

There have also been attempts to replace multiple application access toremote data in mobile devices with a specialized data access client, amatching server extension and an optional middle tier. In thisarrangement rules were used to allow those files that were most likelyto be needed, based on recent history, to be copied to a mobile devicebefore the device disconnected from a network.

SUMMARY OF THE INVENTION

The invention provides a data mashup on a user's device. The preferredand probably most useful device is a mobile one. However, there is noreason to so limit the invention. When the user makes an applicationdata entry, such as a calendar entry for a meeting with a customer, themashup uses rules and data patterns that have been defined by the userto query other relevant information sources to collect relatedinformation about the customer or the meeting, and to cache thecollected information on the device for the user.

BRIEF DESCRIPTION OF THE DRAWING

A better understanding of the invention will be had when the followingdetailed description is read in conjunction with the Drawing in which:

FIG. 1 is a block diagram of an illustrative cache mashup system,including client applications, application caches, application servers,and a message queuing system for communications between these systemcomponents;

FIG. 2 shows illustrative user-defined rules that govern the operationof the system in response to user entries into client applications, suchas calendars, browsers and similar client applications;

FIG. 3 shows one illustrative format of messages that are passed in thesystem of FIG. 1;

FIG. 4 is a simplified and illustrative block diagram of the system ofFIG. 2 to illustrate operations of the invention in response to theentry of a meeting into a client calendar application.;

FIG. 5 shows illustrative process steps performed at a clientapplication, such as a calendar client application;

FIG. 6 shows illustrative process steps performed at an applicationcache, such as a calendar cache application according to the invention;and

FIG. 7 is a block diagram of a laptop computer or other illustrativedevice suitable for practicing the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows a block diagram of a client computer with a number ofIllustrative software applications, which are be used to describe theinvention. For example, client computer 100 contains an address book104, a calendar application 106, a web browser 108 and a customerrelations manager (CRM) 110.

These applications are logically connected to a cache mashup application102 by message queues 112, 114, 116 and 118, which in turn arerespectively connected to caches 128, 130, 132 and 134 that arerespectively associated with the mentioned client applications. Themessage queues are used to pass messages between the client applicationsand the mashup and can be implemented with IBM's Message Queuing system.Each of the caches is also, by way of example, connected to a backendserver that services the respective client application. For example,address book 104 is associated with a backend address server 136,Calendar 106 is associated with backend calendar server 138, and so onfor browser 108 and web server 140, and CRM 110 and server 142. Each ofthe mashup caches is also illustratively associated with a rules andpattern (R&P) module. For example, address cache 128 is associated withR&P 120; calendar cache 130 is associated with R&P 122 and so on for R&P124 and R&P 126 for the browser and CRM caches. These R&P modulescontain information entered by a user of the client computer to controlthe actions that are taken when the user enters or deletes informationin a backend server via one of the client applications.

FIG. 2 shows one illustrative example of a set of rules that a usermight enter into the R&P modules. The focus is primarily on the calendarapplication 106 and calendar cache 130. The example chosen to illustratethe invention is one in which a user wishes a calendar entry for acustomer meeting to initiate a series of actions that automaticallycollects customer information likely to be useful for the user toprepare for the meeting. There is no intention to limit the invention tothis example. It is merely illustrative of the types of actions that auser might find useful. Thus, in R&P 122, the user has entered rule RIthat instructs the calendar cache 130 that for every new scheduledcustomer meeting with Sam, initiate actions to the other clientapplications so that the mashup collects the email address of Sam andemployer company name from the address server. Rule R2 of 122 instructsthe mashup to fetch some recent news articles from a designated newssource, such as the Wall Street Journal, and cache them at browser cache132. Rule R3 instructs the mashup that for a customer meeting with Sam,fetch Sam's most favorite web bookmarks. For R3, the rule would containa social networking URL, such as http://del.icio.us to query for Sam'sbookmarks.

With reference to FIG. 4, which is a simplified and re-arranged systemview to aid this description, as a result of a user entering at 400 acalendar entry for a customer meeting with Sam, a meeting entry is madeinto Sam's calendar at the calendar server 138 via a message sent fromthe calendar client 106 via communication link 402, queue 112, calendarcache 130 and links 404 and 405. This user entered message contains aCOUNT field set to the integer value one (1) to prevent the clientapplication from discarding the message for a reason that will becomeapparent from the following discussion. As that calendar entry is beingmade, calendar cache 130 also queries R&P 122 to determine which, ifany, user rules might be triggered by the contents of the calendarmessage. Since this is a customer meeting with Sam, rules R!, R2, R3 andR4 are triggered. As a result of R1, calendar cache 130 queues a messagein queue 114 via logical connection 406 to the queue 112 that serves theaddress book cache 104 to fetch Sam's company address and his emailaddress from the address server 136. When this message arrives at theaddress cache 128, it triggers rule R2 to fetch and cache the desiredinformation. Of course, it is assumed for this example, that thisinformation for Sam has previously been entered into the address serverby the user. FIG. 3 shows an example of what this message might looklike. In FIG. 3, TYPE is set to ADDR, meaning fetch information from theaddress server. HANDLE is set to Sam to identify the party whose addressinformation is desired. TARGET DATE is set to the date of the meeting;PATTERN might be set to other information specific to the type ofmessage being generated, but is empty for this message in this preferredembodiment; COUNT is set to an arbitrary integer greater than zero toprevent the looping of messages. This will be explained in more detaillater. The purpose of this message to the address book cache is to storeSam's address information from the address server 136 into the user'saddress cache 128 The TARGET DATE prevents the stored addressinformation from being deleted from the address cache before it isneeded.

The original meeting entry message at calendar cache 130 also triggersrules R2, R3 and R4 of the calendar R&P 122. Rule R2 results in thegeneration and queuing in queue 114 of a message to the browser cache132 via logical link 408 and connection 414 to fetch, in this example,recent news articles regarding the company that employs Sam. The HANDLEof rule R2 will contain the company name taken from R&P 122. It is alsopossible to fetch this information from the address book if desired, butthis requires a slightly more complicated application at the calendarcache 130. For this message, rule R2 of R&P 122 contains a user-enteredURL of a desired news source for Sam's company and is stored in PATTERNof the generated message to browser application 108. This might be, forexample, http://www.wsj.com identifying the Wall Street Journal website. Rule R2 could also contain a number, say 10, to limit the numberof news articles that will be retrieved, but in this simplifiedembodiment, the number is placed in the rules of the other clientapplications. This message triggers rule R2 in the browser R&P 124.

Rule R3 also results in a second message to the browser cache 132 tofetch Sam's favorite bookmarks. This message in this example is relatedto social networking web sites to fetch and store in the user's browsercache 132 a number of items that illustrate the likes, or perhapsdislikes, of Sam. In this example, assuming that Sam participates insocial networking, Sam's favorite Web bookmarks are used for thispurpose. TYPE of the message is set to BROWSER to identify the browsercache, HANDLE is set to http://del.icio.us/sam to identify the locationof Sam's stored favorite bookmarks. This particular site is only anexample of course. There can be any number of social networking websites at any given time that a user might wish to use. This messagetriggers rule R1 in the browser R&P 124.

Rule R4 at calendar cache R&P 122 triggers a message to queue 112 to theCRM cache 134 via logical link 410 and connection 416. The purpose ofthis message is to store information about Sam into CRM cache 134 fromthe user's internal CRM server 142. TYPE is set to CRM and HANDLE is setto Sam. Again, COUNT is set to some arbitrary integer greater than zero.This message triggers rule R2 of the CRM R&P 126.

FIG. 5 shows an illustrative flowchart of the steps taken to implementthe invention at the calendar client application. When a user enters anew calendar entry, step 502 at the calendar application generates andsends an appropriate message to the calendar cache to initiateoperations as above described.

FIG. 6 shows illustrative steps at the calendar cache 130 that areperformed in response to the receipt of a message from the calendarclient. Step 602 retrieves the integer in the COUNT field of theincoming message, decrements the value by 1 and stores the resultinginteger back into the COUNT field. Step 604 next examines the value ofthe decremented integer. If it is less than zero (0), step 606 discardsthe message. This prevents incoming requests from generating an infinitenumber of messages as a result of the triggering of other rules thatmight be stored at the various cache R&P's. If the value of thedecremented COUNT is not negative, step 608 determines if this is acustomer meeting entry. If not, calendar cache 130 performs otherappropriate steps in this example, such as merely sending the entry ontothe backend calendar server 138. If this is an entry for a customermeeting, step 610 fetches the customer name from the incoming messageand step 612 searches the calendar R&P 122 to determine which, if any,rules are matched. As each matching rule is found as determined at step614, step 616 executes the rule, which in the typical case causes thecalendar cache 130 to generate an outgoing message to one of the clientapplications, as above described, to initiate an appropriate action tocache the desired information. As mentioned, the meeting date includedin each outgoing message to the client applications prevents the cachesfrom deleting the retrieved information from the caches until after themeeting.

It is noted, that each of the client application caches will performsteps similar to those described above. It is also noted that anapplication cache may delay caching the data described by a queuedrequest to a time just prior to the target date in the request. Forexample, the browser cache might delay retrieving the bookmarksrequested by calendar rule R3 until, say, three days before the calendarmeeting, which is the target date in the respective queued request.

FIG. 7 illustrates a simplified example of an information handlingsystem that may be used to practice the present invention. The inventionmay be implemented on a variety of hardware platforms, includingembedded systems, personal computers, workstations, servers, andmainframes. The computer system of FIG. 7 has at least one processor760. Processor 760 is interconnected via system bus 762 to random accessmemory (RAM) 766, read only memory (ROM) 764, and input/output (I/O)adapter 768 for connecting peripheral devices such as disk unit 720 andtape drive 740 to bus 762. The system has user interface adapter 722 forconnecting keyboard 724, mouse 726, or other user interface devices suchas audio output device 766 and audio input device 768 to bus 762. Thesystem has communication adapter 734 for connecting the informationhandling system to a data processing network 750, and display adapter736 for connecting bus 762 to display device 738. Communication adapter734 may link the system depicted in FIG. 7 with hundreds or eventhousands of similar systems, or other devices, such as remote printers,remote servers, or remote storage units. The system depicted in FIG. 7may be linked to both local area networks (sometimes referred to asintranets) and wide area networks, such as the Internet.

It will be appreciated that the computer system 700 illustrated in FIG.6 is merely illustrative, and is not meant to be limiting in terms ofthe type of system which may provide a suitable operating environmentfor practicing the present invention. While the computer systemdescribed in FIG. 7 is capable of executing the processes describedherein, this computer system is simply one example of a computer system.Many systems are capable of performing the processes of the invention.

Artisans in the field of this invention will quickly realize that thepreferred and disclosed embodiment can have many variations that arewithin the intent and scope of the teaching. It is the intent of theinventor to encompass these variations to the extent possible inaccordance with the state of the applicable relevant art in the field ofthe invention.

1. A method of collecting information regarding an event in a computersystem that includes a plurality of client computer applications, aplurality of client computer caches that temporarily store informationassociated with the applications, a plurality of networked servers thatsemi-permanently store the information associated with the applications,and a message queuing system that provides message transmissionthroughout the system, the method comprising storing at one or more ofthe caches a set of rules, each rule to trigger an event in another oneof the caches, receiving at a first cache a first message from a clientapplication to create an event and to store in the associated serverinformation regarding the event, comparing the first message with a setof rules that are stored in association with the first cache for a matchwith one or more rules associated with the first cache, and for eachrule that matches the first message, generating another message directedto a specified client application cache and directing the specifiedclient application cache to collect and cache specified information fromthe server associated with the specified client application cache. 2.The method of claim 1 wherein the first client computer application is acalendar application associated with a calendar cache and a calendarserver, and a rule stored in association with the calendar cache thatgenerates a message to an address book client cache to collect customerinformation when a customer meeting is entered from the calendarapplication.
 3. The method of claim 1 wherein the first client computerapplication is a calendar application associated with a calendar cacheand a calendar server, and a rule stored in association with thecalendar cache that causes a message to be sent to a social networkingweb site to collect customer information when a customer meeting isentered from the calendar application.
 4. The method of claim 3 whereinthe social networking web site is specified in the rule associated withthe calendar cache.
 5. The method of claim 1 wherein the first clientcomputer application is a calendar application associated with acalendar cache and a calendar server, and a rule stored in associationwith the calendar cache that generates a message to a database tocollect customer information when a customer meeting is entered from thecalendar application.
 6. The method of claim 1 further comprisingincluding in each message a COUNT field having a positive integer, andat each client application cache decrementing the value in the COUNTfield and discarding a message when the decremented value reaches acertain value.
 7. A client computer including a plurality of clientcomputer applications and a plurality of client computer cachesassociated with the client computer applications that temporarily storeinformation associated with the applications, the client computercomprising memory at least a first cache for storing a set of one ormore rules, each rule to trigger the transmission of a message totrigger an event in another one of the caches in response to receipt ofa message from the application associated with the first cache, meansfor receiving at the first cache a first message from the associatedclient application to create an event in a remote server associated withthe first cache and to store in the associated server informationregarding the event, means for comparing the first message with the setof rules that are stored in association with the first cache for a matchwith one or more, and means responsive to each rule that matches thefirst message for generating another message to a specified clientapplication cache directing the specified client application cache tocollect and cache specified information from a remote server associatedwith the specified client application cache.
 8. The client computer ofclaim 7 wherein the first client computer application is a calendarapplication associated with a calendar cache and a remote calendarserver, and a rule stored in association with the calendar cache causesthe generating means to transmit a message to an address book clientcache to collect customer information when a customer meeting is enteredfrom the calendar application.
 9. The client computer of claim 7 whereinthe first client computer application is a calendar applicationassociated with a calendar cache and a calendar server, and a rulestored in association with the calendar cache causes the generatingmeans to transmit a message to a social networking web site to collectcustomer information when a customer meeting is entered from thecalendar application.
 10. The client computer of claim 9 wherein thesocial networking web site is specified in the rule associated with thecalendar cache.
 11. The client computer of claim 7 wherein the firstclient computer application is a calendar application associated with acalendar cache and a calendar server, and a rule stored in associationwith the calendar cache causes the generating means to transmit amessage to a database to collect customer information when a customermeeting is entered from the calendar application.
 12. The clientcomputer of claim 7 further comprising wherein each client applicationcache means has a means for decrementing the value in the COUNT fieldand means for discarding a message when the decremented value reaches acertain value.
 13. A storage medium containing program code forcontrolling a client computer to execute a method of collectinginformation regarding an event in a computer system that includes aplurality of client computer applications, a plurality of clientcomputer caches that temporarily store information associated with theapplications, a plurality of networked servers that semi-permanentlystore the information associated with the applications, and a messagequeuing system that provides message transmission throughout the system,the medium comprising code for storing at one or more of the caches aset of rules, each rule to trigger an event in another one of thecaches, code for receiving at a first cache a first message from aclient application to create an event and to store in the associatedserver information regarding the event, code for comparing the firstmessage with a set of rules that are stored in association with thefirst cache for a match with one or more rules associated with the firstcache, and for each rule that matches the first message, code forgenerating another message directed to a specified client applicationcache and code for directing the specified client application cache tocollect and cache specified information from the server associated withthe specified client application cache.
 14. The medium of claim 13wherein the first client computer application is a calendar applicationassociated with a calendar cache and a calendar server, and a rulestored in association with the calendar cache stimulates code means togenerate a message to an address book client cache to collect customerinformation when a customer meeting is entered from the calendarapplication.
 15. The medium of claim 13 wherein the first clientcomputer application is a calendar application associated with acalendar cache and a calendar server, and a rule stored in associationwith the calendar cache stimulates code to send a message to a socialnetworking web site to collect customer information when a customermeeting is entered from the calendar application.
 16. The medium ofclaim 13 wherein the first client computer application is a calendarapplication associated with a calendar cache and a calendar server, anda rule stored in association with the calendar cache stimulates code togenerate a message to a database to collect customer information when acustomer meeting is entered from the calendar application.
 17. Themedium of claim 13 further comprising code for controlling each cache todecrement a value stored in a field of each received message and codefor discarding a message when the decremented value reaches a certainvalue.
 18. The method of claim 1 wherein the directing of the specifiedclient application cache to collect and cache specified information fromthe server associated with the specified client application cachefurther comprises delaying the retrieving of information until justbefore the specified event.
 19. The client computer of claim 7 whereinthe means for generating another message to a specified clientapplication cache directing the specified client application cache tocollect and cache specified information further comprises means fordelaying the retrieving of information until just before the specifiedevent.
 20. The medium of claim 13 wherein the code for directing thespecified client application cache to collect and cache specifiedinformation from the server further comprises code for delaying theretrieving of information until just before the specified event.